Motivation and Context

When using registerPrompt without any argsSchema the callback will still be typed as the first argument is the input of the argsSchema, which is not the case.

This PR corrects that.

Code:

server.registerPrompt(
  'my_prompt',
  { title: 'My Prompt' },
  ({ authInfo }) => {

Current type:

McpServer.registerPrompt<ZodRawShapeCompat>(name: string, config: {
  ...
}, cb: (args: ShapeOutput<ZodRawShapeCompat>, extra: RequestHandlerExtra<ServerRequest, ServerNotification>) => ...

Correct type:

McpServer.registerPrompt<undefined>(name: string, config: {
 ...
}, cb: (extra: RequestHandlerExtra<ServerRequest, ServerNotification>) => ...

How Has This Been Tested?

Tested in a project using mcp-handler

Breaking Changes

Maybe someone has used the types incorrectly. Unsure if this counts as breaking, as it's a bugfix.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed